Re-enable jms quickstart tests #1541
Conversation
|
When delay is 0 it appears that sometimes the message is 'lost' in the ordering of things starting up. Delay 1 just gives things time to start up fully before a message is created. Can't explain why the message gets lost with 0 but it is working consistently for me in test/IT with a delay set. |
Change wording slightly to say that running Artemis is not required for unit/integration tests
gsmet
force-pushed
the
fix-jms-quickstart-tests
branch
from
160b519 to
b898b43
Compare
Status for workflow
|
| Status | Name | Step | Failures | Logs | Raw logs |
|---|---|---|---|---|---|
| ✖ | Build - JDK 17 | Build with Maven |
Failures | Logs | Raw logs |
Full information is available in the Build summary check run.
Failures
⚙️ Build - JDK 17 #
- Failing: amqp-quickstart/amqp-quickstart-processor tika-quickstart
📦 amqp-quickstart/amqp-quickstart-processor
✖ org.acme.amqp.processor.QuoteProcessorTest.testProcessor line 46 - More details - Source on GitHub
java.lang.AssertionError: Expected 1 items. Only 0 items have been received.
at io.smallrye.mutiny.helpers.test.AssertSubscriber.awaitItemEvents(AssertSubscriber.java:684)
at io.smallrye.mutiny.helpers.test.AssertSubscriber.awaitItems(AssertSubscriber.java:440)
at io.smallrye.mutiny.helpers.test.AssertSubscriber.awaitItems(AssertSubscriber.java:411)
at org.acme.amqp.processor.QuoteProcessorTest.testProcessor(QuoteProcessorTest.java:46)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at io.quarkus.test.junit.QuarkusTestExtension.runExtensionMethod(QuarkusTestExtension.java:1000)
at io.quarkus.test.junit.QuarkusTestExtension.interceptTestMethod(QuarkusTestExtension.java:848)
📦 tika-quickstart
✖ Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:3.1.2:test (default-test) on project tika-quickstart:
Please refer to /home/runner/work/quarkus-quickstarts/quarkus-quickstarts/tika-quickstart/target/surefire-reports for the individual test results.
Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
There was an error in the forked process
1 participant
Scheduing the test message to be published after small delay appears to get around randomness of commented out tests
Check list:
Your pull request:
developmentbranch999-SNAPSHOTversion of Quarkusmvn clean test)mvn clean package -Pnative)mvn clean verify -Pnative)README.mdfile (with build and run instructions)pom.xmlandREADME.md